Data collection system and interface

ABSTRACT

Systems for data measurement and collection are provided. A data collection system may comprise a database configured to store data about objects to be tracked, and optical codes corresponding to specific database entries may be generated, printed, and provided in physical proximity to the object to be tracked. When a user scans the optical code with a mobile electronic device, the mobile electronic device may automatically upload geographic information to the database and may prompt the user to enter measurement information to additionally be uploaded to the database. Sets of optical codes may be configured to collect user-specified types of data, and the optical codes may be provided in printable sheets; virtual visual representations of the sheets may be displayed on an electronic interface, and the virtual visual representations may indicate which of the codes have or have not been registered with the system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/712,642, filed Dec. 12, 2019, which claims the benefit of U.S.Provisional Application No. 62/779,248, filed Dec. 13, 2018, the entirecontents of each of which are incorporated herein by reference.

FIELD

This disclosure relates generally to data collection systems, andparticularly to data collection systems for tracking and measuringphysical objects using optical codes to associate physical objects withmeasured and recorded characteristics thereof.

BACKGROUND

The proliferation of the Internet of things (IoT) has dramaticallyincreased the number of devices capable of collecting and transmittingdata. However, IoT devices are typically designed to collect onlyspecific kinds of data and are designed for specific applications,leading to high development costs and long deployment times. Thus, thereexists a need for a low-cost, customizable data collection system thatcan collect and store different types of data for differentapplications.

BRIEF SUMMARY

As discussed above, there is a need for low-cost, customizable datacollection systems. This need may be addressed by the systems, methods,and techniques disclosed herein for configuring, deploying, and using adata collection system for tracking and measuring characteristics ofphysical objects. The system allows users to define data profiles thatcorrespond to measurable characteristics of particular objects, and toassociate the data profiles with unique optical codes that may bedeployed and physically associated with the physical object to bemeasured. Users may then scan the physically deployed instance of theoptical code with a mobile device (e.g., a smart phone) to cause thedevice to automatically prompt the user to enter certain measured data,to automatically measure certain data, and/or to automatically transmitinformation regarding the measured data for storage.

Embodiments contemplated in the present disclosure may address the needsdiscussed above by decoupling the measurement component of a networkconnected device from the identity of the object to be measured and/orfrom an electronic device for determining the identity of the object tobe measured. Disclosed are devices, systems, and methods for configuringand deploying a customizable data collection system.

To configure the system, a user may generate and store digital entriesthat uniquely correspond to optical codes. The optical codes may beassociated with real world objects via a physical deployment ofinstances of the optical codes, such as one or more printed labels orstickers.

A user may then scan the optical code associated with an object, such asby using a mobile electronic device, to access one or more graphicaluser interfaces for inputting measurements of the object. The device maythen transmit the inputted data associated with the object, in additionto any other automatically measured data regarding the object and/or thetime or nature of the measurement. The transmitted data may be based onany appropriate physical sensor or measurement device, including sensorsintegrated into the device that scanned the optical code and/or sensorsseparate from the device that scanned the optical code, or based onobservations by the user. A physical sensor that is the source of themeasurement does not need to be associated with the object or known tothe data collection system.

In this way, physical embodiments of the optical codes, such as printedlabels generated by the system, may serve as virtual sensors thatidentify the measured object but are not constrained to the measurementcapability of a particular physical sensor to characterize the object.Therefore, the disclosed data collection system may be customized by theuser to collect any type of data in any type of application.

In some embodiments, a first method, for measuring and recording acharacteristic of an object, is provided, the first method comprising:at a device comprising a display, an optical sensor, a GPS sensor, oneor more processors, and memory: detecting, by the optical sensor, anoptical code, wherein the optical code is physically associated with anobject; and in response to detecting the optical code: decoding anidentifying value encoded in the optical code; transmitting geographicinformation from the GPS sensor to a remote server, wherein thegeographic information is transmitted in accordance with the decodedidentifying value; and transmitting information regarding one or moremeasured characteristics of the object, the information regarding theone or more measured characteristics being distinct from the geographicinformation, to the remote server, wherein the information regarding oneor more measured characteristics is transmitted in accordance with thedecoded identifying value.

In some embodiments, the first method comprises: in response todetecting the optical code, displaying a prompt for a user to enterinformation regarding the one or more measured characteristics of theobject.

In some embodiments, the first method comprises: in response todetecting the optical code, automatically reading information regardingthe one or more measured characteristics of the object from a sensorassociated with the device.

In some embodiments of the first method, the sensor is integrated intothe device.

In some embodiments of the first method: the sensor is communicativelycoupled with the device via one or more network communicationinterfaces, and automatically reading information regarding the one ormore measured characteristics of the object from the sensor comprisescausing the device to receive, via the one or more network transmissionsfrom the sensor, a network communication transmission comprisinginformation regarding the one or more measured characteristics.

In some embodiments of the first method, the identifying value uniquelycorresponds to an entry in a database.

In some embodiments, the first method comprises: in response todetecting the optical code, in accordance with a determination thatregistration transmission has not previously been transmitted to theremote server in response to detection of the optical code, displaying aregistration interface comprising a user interface object configured toaccept a user input comprising information associated with registeringthe optical code; detecting an instruction from the user to transmit theinformation associated with registering the optical code; and inresponse to receiving the instruction to transmit the informationassociated with registering the optical code, transmitting aninstruction to the remote server to register the optical code byuniquely associating the entry in the database with the informationassociated with registering the optical code.

In some embodiments of the first method, the information associated withregistering the optical code comprises a name associated with theobject.

In some embodiments of the first method, the identifying value comprisesa URL corresponding to the entry in the database.

In some embodiments of the first method, the optical code comprises a QRcode.

In some embodiments, a device for measuring and recording acharacteristic of an object is provided, the device comprising adisplay, an optical sensor, a GPS sensor, one or more processors, andmemory storing instructions executable by the one or more processors tocause the device to: detect, by the optical sensor, an optical code,wherein the optical code is physically associated with an object; and inresponse to detecting the optical code: decode an identifying valueencoded in the optical code; transmit geographic information from theGPS sensor to a remote server, wherein the geographic information istransmitted in accordance with the decoded identifying value; andtransmit information regarding one or more measured characteristics ofthe object, the information regarding the one or more measuredcharacteristics being distinct from the geographic information, to theremote server, wherein the information regarding one or more measuredcharacteristics is transmitted in accordance with the decodedidentifying value.

In some embodiments a first non-transitory computer-readable storagemedium, storing instructions for measuring and recording acharacteristic of an object, is provided, the instructions configured tobe executed by one or more processors of a device comprising a display,an optical sensor, a GPS sensor, and one or more processors, theinstructions configured to cause the device to: detect, by the opticalsensor, an optical code, wherein the optical code is physicallyassociated with an object; and in response to detecting the opticalcode: decode an identifying value encoded in the optical code; transmitgeographic information from the GPS sensor to a remote server, whereinthe geographic information is transmitted in accordance with the decodedidentifying value; and transmit information regarding one or moremeasured characteristics of the object, the information regarding theone or more measured characteristics being distinct from the geographicinformation, to the remote server, wherein the information regarding oneor more measured characteristics is transmitted in accordance with thedecoded identifying value.

In some embodiments, a second method, for configuring a data collectionsystem, is provided, the second method comprising: at a systemcomprising a display, one or more processors, and memory: detecting afirst user input, wherein the first user input comprises an instructionto generate a set of database entries for monitoring respective objects,and wherein the first user input indicates one or more characteristicsof the objects to be monitored; in response to detecting the first userinput: creating a set of database entries, wherein each entry of the setof database entries is configured to store data regarding the one ormore characteristics of one of the respective objects; and generating aset of optical codes, wherein each code of the set of optical codesuniquely corresponds to one of the database entries created; detecting asecond user input, wherein the second user input comprises aninstruction to display a plurality of images associated respectivelywith a subset of the set of database entries, wherein each image of theplurality of images uniquely corresponds to a respective one of the setof database entries; and in response to detecting the second user input,displaying a dynamic visual representation of the plurality of images,wherein, for each of the plurality of images, the image visuallyindicates whether the system has received registration informationregarding association of a physical instance of the correspondingoptical code with one of the objects.

In some embodiments of the second method, the first user input comprisesa selection by the user of a data profile, wherein the data profileindicates the one or more characteristics of the objects to bemonitored.

In some embodiments of the second method, the dynamic digitalrepresentation of the one or more of the optical codes comprises avisual representation of a sheet of labels, wherein each of the labelscomprises one of the optical codes.

In some embodiments of the second method: the dynamic visualrepresentation indicates that the system has received registrationinformation for a first one of the images by not displaying a firstcorresponding optical code as a part of the first image; and the dynamicvisual representation indicates that the system has not receivedregistration information for a second one of the images by displaying asecond corresponding optical code as a part of the second image.

In some embodiments, the second method comprises: receiving a third userinput indicating an instruction to display information regarding aplurality of measurements associated with one of the database entries ofthe set of database entries; and in response to receiving the third userinput, displaying a chronological list of measurement transmissions,wherein each of the measurement transmissions comprises a time of themeasurement and a data regarding the one or more characteristics.

In some embodiments of the second method, one or more of the measurementtransmissions comprises a photograph transmitted from a portableelectronic device.

In some embodiments, a data-collection system is provided, the systemcomprising a display, one or more processors, and memory storinginstructions executable by the one or more processors to cause thesystem to: detect a first user input, wherein the first user inputcomprises an instruction to generate a set of database entries formonitoring respective objects, and wherein the first user inputindicates one or more characteristics of the objects to be monitored; inresponse to detecting the first user input: create a set of databaseentries, wherein each entry of the set of database entries is configuredto store data regarding the one or more characteristics of one of therespective objects; and generate a set of optical codes, wherein eachcode of the set of optical codes uniquely corresponds to one of thedatabase entries created; detect a second user input, wherein the seconduser input comprises an instruction to display a plurality of imagesassociated respectively with a subset of the set of database entries,wherein each image of the plurality of images uniquely corresponds to arespective one of the set of database entries; and in response todetecting the second user input, display a dynamic visual representationof the plurality of images, wherein, for each of the plurality ofimages, the image visually indicates whether the system has receivedregistration information regarding association of a physical instance ofthe corresponding optical code with one of the objects.

In some embodiments, a second non-transitory computer-readable storagemedium, storing instructions for configuring a data collection system,is provided, the instructions configured to be executed by one or moreprocessors of a system comprising a display and one or more processors,the instructions configured to cause the system to: detect a first userinput, wherein the first user input comprises an instruction to generatea set of database entries for monitoring respective objects, and whereinthe first user input indicates one or more characteristics of theobjects to be monitored; in response to detecting the first user input:create a set of database entries, wherein each entry of the set ofdatabase entries is configured to store data regarding the one or morecharacteristics of one of the respective objects; and generate a set ofoptical codes, wherein each code of the set of optical codes uniquelycorresponds to one of the database entries created; detect a second userinput, wherein the second user input comprises an instruction to displaya plurality of images associated respectively with a subset of the setof database entries, wherein each image of the plurality of imagesuniquely corresponds to a respective one of the set of database entries;and in response to detecting the second user input, display a dynamicvisual representation of the plurality of images, wherein, for each ofthe plurality of images, the image visually indicates whether the systemhas received registration information regarding association of aphysical instance of the corresponding optical code with one of theobjects.

In some embodiments, a data measurement and collection system isprovided, the system comprising: a server configured to: detect a firstuser input, wherein the first user input comprises an instruction togenerate a set of database entries for monitoring respective objects,and wherein the first user input indicates one or more characteristicsof the objects to be monitored; and in response to detecting the firstuser input: create a set of database entries, wherein each entry of theset of database entries is configured to store data regarding the one ormore characteristics of one of the respective objects; and generate aset of optical codes, wherein each code of the set of optical codesuniquely corresponds to one of the database entries created; and amobile electronic device comprising an optical sensor and a GPS sensor,the mobile electronic device configured to: detect, by the opticalsensor, one of the optical codes of the set of optical codes, whereinthe optical code is physically associated with one of the objects; andin response to detecting the optical code: transmit geographicinformation from the GPS sensor to the server; and transmit informationregarding a measurement of the one or more characteristics of theobject, the information regarding a measurement being distinct from thegeographic information, to the server.

In some embodiments of the data measurement and collection system, themobile electronic device is configured to, in response to detecting theoptical code, display a graphical user interface configured to accept auser input indicating the measurement of the one or more characteristicsof the object.

In some embodiments, any one or more features of any of the methods,systems, devices, and computer-readable mediums disclosed above orelsewhere herein may be combined with one another and/or with featuresof any one or more of the other methods, systems, devices, andcomputer-readable mediums disclosed elsewhere herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of the data collection system, according to someembodiments.

FIG. 2 is a flow diagram that illustrates the process for configuringthe data collection system and deploying the tracking codes, accordingto some embodiments.

FIG. 3 is a flow diagram that illustrates the process of using a mobiledevice to collect and transmit information regarding a tracked object,according to some embodiments.

FIG. 4A is an exemplary depiction of an interface for creating a dataprofile, according to some embodiments.

FIG. 4B is an exemplary depiction of an interface for viewing a list ofrecently scanned labels, according to some embodiments.

FIG. 4C is an exemplary depiction of an interface for viewing theproperties of a digital label entry, according to some embodiments.

FIG. 4D is an exemplary depiction of an interface for viewing recentlyreceived data entries for a digital label entry, according to someembodiments.

FIG. 4E is an exemplary depiction of dynamic virtual representation ofdigital label entries associated with a data profile, according to someembodiments.

FIG. 5A is an exemplary depiction of an interface for registering aphysical label, according to some embodiments.

FIG. 5B is an exemplary depiction of an interface for prompting theentry of measurement data, according to some embodiments.

FIG. 5C is an exemplary depiction of an interface for prompting theentry of an event, according to some embodiments.

FIG. 5D is an exemplary depiction of an interface for prompting theentry of a photograph, according to some embodiments.

FIG. 6 is a depiction of physical label as a printed sticker, accordingto some embodiments.

FIG. 7 is a functional block diagram of a computer in accordance withsome embodiments.

DETAILED DESCRIPTION

Described herein are exemplary embodiments of systems, devices, andmethods for configuring and deploying a customizable data collectionsystem. The system provides for the creation of customizable dataprofiles that correspond to real-world objects having unique measurablecharacteristics. The system provides for the creation of unique opticalcodes that may be deployed and physically associated with objects to bemeasured. In this way, the optical codes may uniquely identify eachmeasured object in the system. The system allows for the collection ofdata corresponding to any measurable or observable characteristic of anobject by receiving data transmitted by a mobile device that hasdetected the optical code associated with the object.

FIG. 1 illustrates a system 100 for configuring and deploying acustomizable data collection system for tracking and/or measuringcharacteristics of real-word objects, according to some embodiments. Insome embodiments, the system comprises a web service and a mobileapplication. System 100 includes a terminal 102 for configuring andmanaging the system, a physical label 104 for identifying an object 106,a mobile device 108 for measuring, entering, and/or transmitting dataregarding object 106, a server 110 to host the system and to store datacollected by the system, a printer 112 for generating physical labels,and a networking device 114 to enable communication between terminal102, mobile device 108, and server 110.

System 100 may generate and store digital label entries in the systemand generate optical codes that are uniquely associated with the labelentries. A digital label entry is a data object that represents aphysical object 106 in the system. The digital label entries may bestored in server 110 and/or in any suitable storage system associatedwith server 110. In some embodiments, a digital label entry may bestored as an entry in a database. Each digital label entry may beidentified in system 100 by a universally unique identifier (UUID).

System 100 may generate physical labels 104 based on the optical codes.In some embodiments, the optical code may be printed on a physical label104 by printer 112. A physical label 104 may be deployed by physicallyassociating the label 104 with an object 106 to be measured. In thisway, the optical code associated with a physical label 104 may uniquelyidentify an object 106 in within system 100. When a user scans anoptical code with mobile device 108, the device may transmit data toserver 110 or may prompt the user to enter data regarding thecorresponding object 106 to be transmitted to server 110. Server 110 mayreceive and store data transmitted by mobile device 108 and associatethe data with the object's corresponding digital label entry withinsystem 100.

System 100 may be used to collect data regarding any measurable orobservable characteristic of an object. For example, system 100 maycollect data regarding temperature of an object, ambient temperaturearound an object, pressure inside a tank or line, fluid level inside atank, humidity, ambient light, weight, speed, location, altitude, mass,density, voltage, current, power, or any other measurable quantity.Alternatively, system 100 may collect data regarding whether a machineis on or off, whether a package is damaged or undamaged, whether apackage is delivered or undelivered, how many units a machine hasmanufactured, whether a valve is open or closed, whether a door is openor closed, or any other observable status of an object.

Terminal 102 may be a host computer connected to a network, a clientcomputer, or a server. Terminal 102 can also be any suitable type ofmicroprocessor-based device, such as a personal computer, workstation,server, videogame console, or handheld computing device, such as a phoneor tablet.

Mobile device 108 may be a computer, a smartphone, a tablet, a barcodescanner, a QR scanner, or other type of microprocessor-based device witha suitable optical sensor. In some embodiments, the optical sensor maybe a camera.

Server 110 may be a database server, a web server, an applicationserver, or any type of microprocessor-based device suitable fortransmitting, receiving, and storing data. Server 110 may comprisemultiple servers that may be co-located or located at differentlocations. Server 110 may comprise cloud computing and storagesolutions.

Networking device 114 may be a server, a cellular communicationsnetwork, or other suitable type of interconnected communications systemthat allows communication between terminal 102, mobile device 108, andserver 110. Networking device 114 can implement any suitablecommunications protocol and can be secured by any suitable securityprotocol. The network can comprise network links of any suitablearrangement that can implement the transmission and reception of networksignals, such as wireless network connections, T1 or T3 lines, cablenetworks, DSL, or telephone lines.

FIG. 2 illustrates a method 200 for configuring and deploying the datacollection system. In some embodiments, method 200 may be performed at asystem such as system 100 discussed above with reference to FIG. 1. Insome embodiments, method 200 may enable a user of systems describedherein to configure and deploy one or more aspects of a data collectionsystem, including configuring the system to collect certain types ofdata, generating physical labels that correspond to entries within thesystem, and associating the labels with real-world objects to identifythe objects within the system.

At step 202, a data profile is created that corresponds to a class ofobjects to be measured or tracked. The data profile is a data objectthat defines the types of data that digital label entries in the systemmay accept. For example, a logistics tracking data profile may bedefined to accept location data. A digital label entry based on such adata profile may only accept data based on location. The data profilemay be stored in server 110 and/or in any suitable storage systemassociated with server 110. In other embodiments, system 100 may prompta user to create a data profile by displaying a prompt at terminal 102,or a user may initiate the creation of a data profile at terminal 102.

At step 204, the characteristics of the data profile are defined. Thecharacteristics of the data profile correspond to particularcharacteristics of a class of objects that the system may be used tomeasure and record.

In some embodiments, the characteristics of the data profile may bedefined by a user at terminal 102. System 100 may display an interfaceat terminal 102 for defining the characteristics of a data profile.Using the interface, the user may enter characteristics to define thedata profile. In response to detecting the user input, terminal 102 maytransmit the user-entered characteristics to server 110. The transmitteddata profile characteristics may be stored in server 110, and server 110may associate the characteristics with the data profile object createdat step 202.

The characteristics may correspond to any measurable or observablefeature of an object. For example, a characteristic may correspond to ameasurable feature of an object, such as temperature or geographicallocation. Alternatively, a characteristic may correspond to anobservable state of an object, such as whether it is damaged orundamaged. The data profile may be configured to accept photographs. Thedata profile may also be configured to accept timestamp informationcorresponding to the time when a corresponding optical code is scannedor when data is received.

In addition to measurable characteristics, the data profilecharacteristics may also be defined in terms of events associated withthe data profile. For example, a logistics tracking profile may bedefined to have “Shipped” or “Delivered” events. If a data profile isdefined by events, mobile device 108 may prompt a user to choose whichevent has occurred when the user scans an optical code associated withthat data profile. If a data profile is defined by events, the interfaceof mobile device 108 may be dynamically populated based on those eventswhen a user scans an optical code associated with the data profile.Rather than prompting a user to enter a measurement, mobile device 108may prompt the user to choose which event has occurred from a predefinedlist of events that is dynamically populated based on thecharacteristics of the data profile.

Events may be designated as “final.” After a final event has beenreceived by the system, the corresponding digital label entry in thesystem will no longer accept data and the corresponding optical codewill no longer be active.

The characteristics of a data profile may be defined based on individualmeasurements or events (e.g. temperature and/or location), selectedone-at-a-time by a user. For example, a data profile may be defined tohave a temperature characteristic, a location characteristic, or both.Alternatively, a data profile may be defined based one or morepre-defined “data models,” or groups of measurements or events that areselected, by a user, as a group. A data model is a predefined scheme,which may be stored as a data object, that comprises combinations ofpossible data profile characteristics. Data models may be stored inserver 110 and/or in any suitable storage system associated with server110. A data model may be generated automatically by the system or may bemanually defined by a user.

A data profile defined based on a data model may be defined to have allof the characteristics associated with the data model. For example, a“Temperature” data model may comprise a temperature characteristic and alocation characteristic. If a data profile is defined based on the“Temperature” data model, the data profile will accept temperature andlocation data. Thus, data models may be created and used to define dataprofiles more quickly.

Characteristics of a data profile may be mandatory or optional. If acharacteristic is mandatory, data regarding that characteristic must betransmitted each time a user scans an optical code associated with thatdata profile. For example, when a user scans a label associated with alogistics tracking profile, the profile may require location data to betransmitted. Alternatively, characteristics of a data profile may beoptional. For example, a logistics tracking profile may permit, but notrequire, a photograph to be transmitted each time a label associatedwith that data profile is scanned.

At step 206, digital label entries are created. Digital label entriesare data objects that represent physical objects in the system. Eachdigital label entry may be associated with a data profile and stored inserver 110 and/or in any suitable storage system associated with server110. A digital label entry may be an entry in a database.

A digital label entry may be generated and stored automatically byserver 110. Alternatively, a digital label entry may be created inaccordance with one or more instructions executed by a user at terminal102. System 100 may display an interface for a user at terminal 102.Using the interface, the user may instruct the system to generate andstore a certain number of digital label entries based on a particulardata profile. In response to detecting the user input, terminal 108 maytransmit the user input to server 110. Based on the transmitted data,server 110 may generate and store the number of digital label entriesspecified by the user and store the digital label entries in associationwith server 110. Server 110 may generate and store data associated witheach digital label entry that identifies its data profile.

In some embodiments, a digital label entry may not correspond to aparticular physical object when it is generated. A digital label entrymay not correspond to a particular physical object until an optical codecorresponding to the digital label entry has been associated with anobject, such as upon registration of the optical code by an end user thefirst time the optical code is scanned by a mobile device (e.g., mobiledevice 108). Similarly, a digital label entry may not contain anymeasurement data when it is generated. A digital label entry may notcontain any measurement data until a corresponding optical code has beenscanned by a mobile device 108 and data corresponding to an object hasbeen transmitted to the system and stored in association with thedigital label entry.

The system may generate any number of digital label entries andassociated physical labels corresponding to a particular data profile.Therefore, the system may collect data corresponding to any number ofobjects, up to and including thousands of objects, millions of objects,billions of objects, or more.

A digital label entry may be associated with further data objects thatrepresent information corresponding to the digital label entry. Forexample, a digital label entry may be associated with further dataobjects that contain information that identifies the data profileassociated with the digital label entry, identifies the optical codeassociated with the digital label entry, indicates whether the opticalcode associated with the digital label entry has ever been scanned,indicates the number of times the optical code associated with thedigital label entry has been scanned, and/or other informationcorresponding to the digital label entry. Additionally, a digital labelentry may be associated with further data objects that containmeasurement data received by the system corresponding to the digitallabel entry.

At step 208, the system may generate and store unique optical codescorresponding to each digital label entry. Each optical code may encodeinformation that uniquely identifies a digital label entry. The opticalcode may be a barcode, a QR code, or other optical code suitable forencoding data that uniquely identifies a digital label entry. In someembodiments, the optical code may encode a uniform resource identifier(URI), a uniform resource name (URN), and/or a uniform resource locator(URL).

The optical codes may be generated and stored by server 110. Eachoptical code may be stored in association with an entry in a database.Server 110 may generate an optical code automatically each time itgenerates and stores a digital label entry. Server 110 may generate andstore additional data associated with the optical code that identifiesthe digital label entry to which the optical code corresponds. In someembodiments, the data may comprise a pointer.

At step 210, physical labels 104 are generated based on the opticalcodes. Physical labels 104 may be physical printed labels suitable forphysical deployment into physical environments in which tracked/measuredobjects exist, and the physical labels may correspond to a plurality ofrespective digital label images that are printed onto the respectivephysical labels. Server 110 may generate and store digital label imagescorresponding to each digital label entry. Each digital label image maybe stored in association with an entry in a database. Each digital labelimage may comprise an optical code that is readable by a mobile device108. Each digital label image may contain information about the digitallabel entry to which the optical code corresponds. For example, thedigital label entry may indicate the corresponding data profile, theUUID associated with the digital label entry, the name of theorganization using the system, and/or other information.

Each digital label image may also contain iconography corresponding tocharacteristics of the associated digital label entry. In someembodiments, the digital label image may depict icons that correspond tothe measurements accepted by the label's data profile. For example, athermometer icon may be included in the digital label image to indicatethat the label's corresponding data profile accepts temperaturemeasurements. In other embodiments, the digital label image may alsocontain colors that correspond to the label's data profile, the type ofmeasurements accepted by the label, or other information.

Server 110 may generate additional images for printing a plurality ofphysical labels. For example, server 110 may generate a printable formimage, or “sheet,” that comprises a plurality of digital label imagesarranged in a manner suitable for printing the digital label images onindividual stickers. In some embodiments, a sheet may comprise aplurality of digital label images arranged into a grid or array suitablefor printing the labels on commercially available adhesive label paper,such as Avery 5163 Shipping Labels.

In some embodiments, server 110 may modify one or more digital labelimages corresponding to each digital label entry. For example, in someembodiments, server 110 may modify a digital label image based onwhether the corresponding optical code has ever been scanned. If theoptical code has been scanned, server 110 may modify the correspondingdigital label image by obscuring the optical code, removing the opticalcode, and/or modifying the optical code, such as by replacing theoptical code with “In use” to prevent a user from re-printing and/orre-placing another label bearing the same image in association withanother physical object. In some embodiments, digital label imagesdisplaying an “In Use” indicator may continue to be graphicallydisplayed by the system as a part of the sheet on which they arelocated, thereby graphically representing the state of thephysically-deployed printed labels, in which “In Use” labels may havebeen removed from the physical printed sheet and placed in associationwith a physical object, and in which labels that are not yet “In Use”may not yet have been removed from the physical printed sheet. Server110 may dynamically generate the digital label images and printable formimages each time physical labels 104 are displayed and/or printed basedon the most recently received data.

Physical labels 104 may be printed by printer 112 based on digital labelimages and/or printable form images. Physical labels 104 may be deployedby being physically associated with physical objects 106 to identify theobjects 106 in system 100, such as by being placed in physical proximityto the physical object. For example, labels or tracking packagelocations may be attached to the package itself. Alternatively oradditionally, physical labels 104 may be deployed by being physicallyassociated with a sensor from which data may be read. For example,labels for monitoring temperature of a room may be placed next to athermometer, and labels for monitoring a fuel label may be placed nextto a fuel gauge. In some embodiments, physical labels 104 may beadhesive stickers that can be attached to objects 106 to be measuredand/or tracked and/or separate sensors.

At step 212, the system may display, at terminal 102, a virtualrepresentation of one or more digital label entries associated with aparticular data profile. In some embodiments, the system may display thevirtual representation in response to an input from a user at terminal102. In some embodiments, the virtual representation may comprise one ormore digital label images associated with a data profile. In otherembodiments, the virtual representation may comprise a particulararrangement (e.g., sheet) of digital label entries, such as theprintable image form that comprises a plurality of digital label imagesin an arrangement suitable for printing.

In some embodiments, server 110 may dynamically generate the content ofthe virtual representation each time it is requested by a user and/or bya component of the system. For example, in some embodiments, server 110may generate a virtual representation of the digital label entries basedon the optical code associated with each digital label entry, the dataprofile associated with each digital label entry, the name of a digitallabel entry assigned by the user, and/or other information. The systemmay display, on terminal 102, the virtual representation generated byserver 110. In other embodiments, server 110 may dynamically generatethe virtual representation based on a determination whether the opticalcode associated with a digital label entry has previously been scannedand/or registered. For example, in accordance with a determination thatthe optical code associated with a digital label entry has previouslybeen scanned and/or registered, server 110 may remove the optical codefrom the virtual representation. In other embodiments, server 110 mayreplace the optical code with “In use” to prevent the user fromre-assigning the label to a second physical object.

FIG. 3 illustrates a method 300 for using a mobile device 108 to collectdata. In some embodiments, method 300 may be performed at a system suchas system 100 discussed above with reference to FIG. 1. In someembodiments, method 300 may enable an end user using a portableelectronic device such as a smart-phone to scan an optical code ofsystem 100 in order to cause the portable electronic device toautomatically upload certain information to a server of system 100 forstorage in a database; in this way, the scanned optical code mayfunction in conjunction with the portable electronic device as part of avirtual sensor for measuring and recording one or more characteristicsof a tracked and/or monitored object associated with the optical code.

At step 302, mobile device 108 scans an optical code associated with anobject 106. Mobile device 108 may be a smartphone, a tablet, a barcodescanner, a QR scanner, or other device with an optical sensor capable ofscanning and decoding the optical code. In some embodiments, scanningthe code may comprise detecting the code using a camera of mobile device108. Mobile device 108 may decode the optical code to extract one ormore pieces of identifying information (e.g., unique identifyinginformation encoded in the optical code and not encoded in other opticalcodes in the system) and use the decoded information to communicate withserver 110. In some embodiments, the decoded information may comprise aURI, URN, and/or URL that mobile device 108 may use to locate and accessone or more local or remote network resources, such as by opening aninternet-accessible webpage in a web browser to communicate with server110. Mobile device 108 may communicate with server 110 by networkingdevice 114.

The decoded information may cause mobile device 108 to transmitinformation to server 110 that allows server 110 to identify the digitallabel entry associated with the optical code. Based on the informationtransmitted by mobile device 108, server 110 may transmit information tomobile device 108, such as the identity of the digital label entryassociated with the optical code, a name previously assigned to thedigital label entry by a user, whether the optical code has previouslybeen scanned, how many times the optical code has been scanned, the dataprofile of the digital label entry, past measurement data, the types ofdata accepted by the data profile, whether data is mandatory oroptional, or other information. Server 110 may transmit instructions tomobile device 108, such as instructions from a website accessed bymobile device 108, to cause mobile device 108 to automatically executeone or more processes and/or display one or more interfaces to receive,record, and transmit measurement/tracking information from mobile device108 to server 110. Server 110 may transmit information to mobile device108 confirming receipt of the information transmitted by mobile device108. Server 110 may also update a data object associated with thedigital label entry corresponding to the optical code to indicate thetotal number of times the optical code has been scanned.

At step 304, system 100 determines whether the optical code haspreviously been “registered.”

When an optical code is detected by a mobile device 108, the system mayprompt the user to “register” the code. To register the optical code,mobile device 108 may display an interface prompting the user to enter aname to be associated with the optical code. The name may correspond tothe physical object associated with the code, a physical sensor (e.g., aphysical measuring device such as a thermometer, a speedometer, a fuellevel gauge, etc.) associated with the optical code, or otherinformation. For example, the name may be an order number, airway bill,house airway bill, product identification number, room number,refrigerator number, package information, or any other name. The nameneed not be unique, though in some embodiments it may be unique, and insome embodiments the system may require the name to be unique. Mobiledevice 108 may transmit, to server 110, the name entered by the user.Server 110 may store, in a data entry, the name entered by the user andassociate the data entry with the optical code's corresponding digitallabel entry. Server 110 may also update data associated with thecorresponding digital label entry to indicate that the correspondingoptical code has been registered.

If a code has been registered, mobile device 108 may not issue aregistration prompt after subsequent scans of the code. If the userfails to register the code after being prompted, the system may notupdate information associated with the corresponding digital label entryin the system to indicate that the code has been registered, and mobiledevice 108 may issue a registration prompt after a subsequent scan ofthe code.

In some embodiments, after receiving, from mobile device 108,information indicating that an optical code has been scanned, server 110may access data associated with the optical code determine whether theoptical code has previously been registered. For example, server 110 mayidentify the digital label entry associated with the optical code, andaccess a data object associated with the digital label entry that storesinformation indicating whether the optical code has previously beenregistered. Server 110 may determine, based on the data, whether theoptical code has previously registered and transmit, to mobile device108, information indicating whether the optical code has previously beenregistered.

At step 306, based on a determination that the optical code has notpreviously been scanned, mobile device 108 may display an interfaceprompting the user to register the optical code. As above, to register acode, mobile device 108 may display an interface prompting the user toenter a name to be associated with the code.

In response to detecting an input, such as a name, from the user, mobiledevice 108 may transmit, to server 110, the information entered by theuser. Server 110 may store, in a data object associated with the digitallabel entry corresponding to the optical code, the name entered by theuser. Additionally, server 110 may store, in a data object associatedwith the digital label entry corresponding to the optical code,information indicating that the optical code has been registered and/orinformation indicating that the optical code has been scanned.

At step 308 mobile device 108 may automatically transmit data to server110. In some embodiments, mobile device 108 may have access to certaindata without any input or any further manual intervention from the user.For example, mobile device 108 may have one or more integrated sensors,such as GPS sensors, temperate sensors, optical sensors, speedometers,presence sensor, capacitive sensors, pressure sensors, accelerometers,gyroscopes, altimeters, or other sensors, such that the device mayaccess and transmit data automatically, without any input or any furthermanual intervention from the user. In some embodiments, informationaccessed from the one or more sensors may be information detected by andread from the one or more sensors in response to the device scanning theoptical code, while in some embodiments the information may beinformation that was detected by the one or more sensors before scanningthe optical code, such as information read from the one or more sensorin accordance with a predefined schedule by which device 108automatically pulls (and temporarily or permanently stores) data fromthe one or more sensors. Alternatively, mobile device 108 may be able toautomatically, without any input or any further manual intervention fromthe user, access and transmit data from sensors not integrated intomobile device 108. For example, mobile device 108 may communicate withsensors over Bluetooth, Bluetooth Low Energy, Zigbee, or othercommunication protocol to automatically retrieve data reflectingmeasurements made by one or more sensors not physically integrated intodevice 108.

In some embodiments, mobile device 108 may ask the user for permissionto access and/or transmit certain data from its integrated sensorsand/or other sensors.

Server 110 may store the data automatically transmitted by mobile device108. The data may be stored as one or more entries in a database. Server110 may generate and store data objects corresponding to eachmeasurement transmitted by mobile device 108 and received by server 110.The data objects may be associated with the digital label entrycorresponding to the optical code. Server 110 may store additional datacorresponding to each measurement, such as the time that the data wasreceived by server 110. Server 110 may transmit information to mobiledevice 108 confirming receipt of the data automatically transmitted bymobile device 108.

At step 310, mobile device 108 may display an interface prompting theuser to enter data required by the data profile to which the opticalcode corresponds. As above, characteristics of a data profile may bemandatory; that is, mobile device 108 must, in some embodiments,transmit data corresponding to such characteristics each time acorresponding optical code is scanned. In some embodiments, mobiledevice 108 may automatically transmit mandatory data to which it hasaccess without any input or any further manual intervention from theuser, as in step 306, above. However, in some embodiments, such as thosein which mobile device 108 does not have access to mandatory datarequired by the data profile, mobile device 108 may display an interfaceprompting the user to enter mandatory data. In some embodiments, mobiledevice 108 may display an interface prompting the user to entermandatory data when the data is to be read from a measuring device thatis not configured for network communication with mobile device 108. Forexample, the user may be required to enter a temperature reading from anexternal temperature sensor, such as a wall-mounted,non-network-connected thermometer.

At step 312, mobile device 108 may, in response to an input from theuser, such as a measurement value or an event selected from a list,transmit mandatory data to server 110. Server 110 may store themandatory data transmitted by mobile device 108. The data may be storedas one or more entries in a database. Server 110 may generate and storedata objects corresponding to each mandatory measurement transmitted bymobile device 108 and received by server 110. The data objects may beassociated with the digital label entry corresponding to the opticalcode. Server 110 may store additional data corresponding to eachmandatory measurement, such as the time that the data was received byserver 110. Server 110 may transmit information to mobile device 108confirming receipt of the mandatory data transmitted by mobile device108.

At step 314, mobile device 108 may display an interface prompting theuser to enter data permitted, but not required, by the data profile towhich the optical code corresponds. As above, characteristics of a dataprofile may be optional; that is, data corresponding to suchcharacteristics may be transmitted by mobile device 108 automaticallyafter scanning an optical or upon detecting in input from a user, but isnot required by the data profile. In some embodiments, mobile device 108may automatically transmit optional data to which it has access withoutany input or any further manual intervention from the user, as in step306, above. However, in some embodiments, such as when mobile device 108does not have access to optional data required by the data profile,mobile device 108 may display an interface prompting the user to enteroptional data. For example, mobile device 108 may display a promptasking if the user wishes to enter a humidity reading from an externalhumidity sensor, such as a wall-mounted, non-network-connectedhygrometer. In response to the prompt, the user may enter a measurementvalue to be transmitted to server 110, or decline to enter a value.Additionally or alternatively, mobile device 108 may display a promptasking if the user wishes to transmit a photograph of the measuredobject. In response to the prompt, the user may take a photograph of themeasured object that will be transmitted by mobile device 108, choose aphotograph stored in the memory of mobile device 108 to be transmittedby mobile device 108, or neither.

At step 316, mobile device 108 may, in response to an input from theuser, transmit optional data to server 110. Server 110 may store theoptional data transmitted by mobile device 108. The data may be storedas one or more entries in a database. Server 110 may generate and storedata objects corresponding to each optional measurement transmitted bymobile device 108 and received by server 110. The data objects may beassociated with the digital label entry corresponding to the opticalcode. Server 110 may store additional data corresponding to eachoptional measurement, such as the time that the data was received byserver 110. Server 110 may transmit information to mobile device 108confirming receipt of the optional data transmitted by mobile device108.

In some embodiments, system 100 may not require authentication or proofof the identity of the user. That is, any user who has access to anoptical code and/or the information encoded therein may transmit datacorresponding to the optical code. Furthermore, in some embodiments,mobile device 108 may not transmit data that identifies the device thatscanned the code and/or the user of the device that scanned the code.One or both of these features may increase anonymity of end userssubmitting measurements, thereby mitigating privacy concerns forend-users by creating a system that tracks and/or measures objectsrather than tracking and/or measuring users or devices. Alternately, insome embodiments, system 100 may be configured to require userauthentication and/or to record data tracking devices and/or users thatupload measurements or other information; in some embodiments, system100 may be able to be configured by a user in order to change one ormore settings regarding anonymity, authentication, and/or user/devicetracking.

In some embodiments, in addition to storing data received from mobiledevice 108, server 110 may process data received from mobile device 108.For example, if mobile device 108 transmits GPS coordinates, server 110may process the coordinates to associate the object with a particularbuilding, such as a warehouse or the like, based on a lookup table orother information available to server 110.

FIGS. 4A-E show various graphical user interfaces 402 a-402 e forconfiguring and managing a data collection system, in accordance withsome embodiments. Interfaces 402 a-402 e allow for the creation of dataprofiles and viewing information regarding digital label entries. Theinterfaces allow a user to view a list of one or more digital labelentries and view information and data associated with a single dataentry. The interfaces also allow a user to view a virtual representationof digital label images associated with one or more digital label entry.

In some embodiments, interfaces 402 a-402 e may be displayed by terminal200 of system 100. In other embodiments, interfaces 402 a-402 e may bedisplayed by any electronic computing device, such as a laptop computer,desktop computer, smart-phone, tablet, or other electronic computingdevice configured to display one or more of interfaces 402 a-402 e andto receive one or more inputs from a user, as discussed herein, tocontrol the operation of the interface and operation of a datacollection system such as system 100. In some embodiments, execution ofall or part of method 200, as discussed above, may include displayingone or more of the interfaces shown in FIGS. 4A-E.

Below, interfaces 402 a-402 e are discussed with respect to FIGS. 4A-4Ein greater detail. Interfaces 402 a-402 e may, in some embodiments, beinterrelated interfaces of a single program or application configured tobe used in connection with one another. For example, each of theinterfaces 402 a-402 e may be different screens that are selectivelyaccessible from a mobile application or other computer programconfigured to work in conjunction with one or more electronic devices inorder to configure and manage a data collection system.

FIG. 4A shows data profile definition interface 402 a, according to someembodiments. Data profile creation interface 402 a may, in someembodiments, be an interface configured to allow a user to create ormodify a data profile by naming the profile and defining characteristicsto be associated with the data profile.

In some embodiments, data profile definition interface 402 a maycomprise profile name field 404. In some embodiments, profile name field404 may be a text field configured to accept input from a user. In someembodiments, a user may enter a name in profile name field 404 to beassociated with the data profile.

In some embodiments, data profile definition interface 402 a maycomprise one or more characteristic toggle icons 406 a-406 c that allowa user to select pre-defined characteristics to be associated with thedata profile. In some embodiments, a user may select one or more ofcharacteristic toggle icons 406 a-406 c to associate the correspondingcharacteristic with the data profile. In the example for FIG. 4A,characteristic toggle icons 406 a-406 c may allow a user to choosewhether a data profile accepts pictures, whether a data profile requestsinformation regarding whether or not an object is damaged, and/orwhether a digital label entry and/or optical code associated with thedata profile is disabled after a final event is received. Someembodiments may allow a user to choose whether or not additionalpre-defined characteristics are associated with a data profile. In someembodiments, characteristic toggle icons 406 a-406 c may be interactiveaffordances, in that they may be clicked, tapped, pressed, or otherwiseselected in order to indicate selection or deselection of thecorresponding characteristic.

In some embodiments, data profile definition interface 402 a maycomprise one or more characteristics fields 408. In some embodiments,characteristics field 408 may be a text field configured to accept inputfrom a user. In some embodiments, characteristics field 408 may beconfigured to allow a user to enter text corresponding to one or morecharacteristics (for example, multiple characteristics may be delineatedby commas, semicolons, or another suitable notation). In someembodiments, characteristics field 408 may be configured to acceptmeasurement characteristics, event characteristics, and/or othercharacteristics to be associated with the data profile.

FIG. 4B shows digital label entry list interface 402 b, according tosome embodiments. Digital label entry list interface 402 b may, in someembodiments, be an interface configured to allow a user to view a listof and/or select one or more digital label entries.

In some embodiments, digital label entry list interface 402 b may beconfigured to allow a user to sort and/or filter a list of digital labelentries according to various criteria. For example, in some embodiments,digital label entry list interface 402 b may comprise filter field 410.In some embodiments, filter field 410 may allow a user to inputinformation causing digital label entry list interface 402 b to filterthe list of digital label entries according to some criteria. In someembodiments, filter field 410 may be a text field configured to acceptinput from a user. A user may enter text causing the interface to modifythe list of digital label entries according to the filtering criteriaentered by the user in filter field 410, such as to only show digitallabel entries having one or more characteristics or features that matchthe text entered into filter field 410. In some embodiments, filterfield 410 may be a drop-down menu, in that, when selected by a user,digital label entry list interface 402 b may display a list ofpre-defined criteria from which the user may choose to filter the listof digital label entries. For example, a user may choose to filter thelist of digital label entries by data profile, by time elapsed since thedigital label entry was created, by time elapsed since the digital labelentry received data, by measurement characteristic, by whether a digitallabel entry has been registered, or by other property.

In other embodiments, filter field 410 may allow a user to inputinformation causing digital label entry list interface 402 b to sort thelist of digital label entries according to some criteria. In someembodiments, a user may enter text causing the interface to modify thelist of digital label entries according to the sorting criteria enteredby the user in filter field 410. In other embodiments, filter field 410may be a drop-down menu, in that, when selected by a user, digital labelentry list interface 402 b may display a list of pre-defined criteriafrom which the user may choose to sort the list of digital labelentries. For example, a user may choose to sort the list of digitallabel entries by data profile, by date when each digital label entry wascreated, by date when the digital label entry received data, by thenumber of times data has been received corresponding to the digitallabel entry, and/or by one or more other properties.

In some embodiments, digital label entry list interface 402 b maycomprise one or more list entry 412. Each list entry may correspond toone digital label entry. In some embodiments, each list entry maydisplay information associated with the corresponding digital labelentry. For example, each list entry may display a name, data profile,registration time, time when a final event was received, the number ofmeasurement events received, and/or other information associated withthe digital label entry. As shown in FIG. 4B, label entry 412 shows thename associated with a digital label entry entered by a user at the timeof registration (“5551212”), the data profile associated with thedigital label entry (“Quality Assurance”), the time when the digitallabel entry was registered, and the number of events received associatedwith the digital label entry (“2 Events”).

In some embodiments, list entries 412 may be an interactive affordance,in that it may be tapped, clicked, pressed, or otherwise selected inorder to active functionality. In some embodiments, digital label entrylist interface 402 b may be configured to allow a user to select a listentry 412 to cause the interface to display further informationassociated with the corresponding digital label entry, such as a digitallabel entry properties interface 402 c, described below.

FIG. 4C shows digital label entry properties interface 402 c, accordingto some embodiments. Digital label entry properties interface 402 c may,in some embodiments, be an interface configured to show one or moreproperties associated with a single digital label entry.

In some embodiments, digital label entry properties interface 402 c maycomprise one or more property fields 414 a-414 f. A property field maydisplay information regarding one or more properties associated with adigital label entry. A property field may display any propertyassociated with the digital label entry. For example, each propertyfield may display an account name, registration name, UUID, data model,data profile, time of registration, time when the last event wasreceived, the total number of events received, whether the digital labelentry has received a final entry, whether the digital label entry hasbeen registered, and/or other information associated with the digitallabel entry. As shown in FIG. 4C, property fields 414 a-414 f display,respectively, a digital label entry's account name (“PharmaCo, Inc”),registration name (“678345”), UUID, data model (“GPS and TemperatureQRSensor”), data profile (“Logistics Tracking”), and time ofregistration.

FIG. 4D shows data history interface 402 d, according to someembodiments. Data history interface 402 d may, in some embodiments, bean interface configured to show one or more data entries associated witha digital label entry.

In some embodiments, data history interface 402 d may comprise one ormore data entries 416 a-416 f. A data entry may display one or morepieces of information associated with a digital label entry. Forexample, a data entry may display a measurement value and a timestampvalue. In some embodiments, a data entry may display a photograph. Adata entry may correspond to one or more measurements received, frommobile device 108, when a digital label entry's corresponding opticalcode was scanned by mobile device 108 and corresponding information wastransmitted from mobile device 108. As shown in FIG. 4D, data entries416 a-416 f may be displayed in reverse chronological orders. In otherembodiments, data entries may be displayed in chronological order, bymeasurement type, or other ordering scheme. As shown in FIG. 4D, dataentries 416 a-416 f display, respectively, a “Warehouse Departure”event, a “Temperature” measurement, a first “Location Update,” a“Warehouse Arrival” event, a second “Temperature” measurement, and asecond “Location Update.”

FIG. 4E shows virtual label interface 402 e, according to someembodiments. Virtual label interface 402 e may, in some embodiments, bean interface configured to show one or more visual representations ofinformation associated with digital label entries. In some embodiments,virtual interface 402 e may comprise one or more digital label images417 associated with one or more digital label entries. In otherembodiments, virtual interface 402 e may comprise one or more digitallabel images 417 corresponding to a single data profile.

In some embodiments, virtual label interface 402 e may comprise aparticular arrangement (e.g., a “sheet”) of digital label images 417,such as an arrangement forming a printable image (e.g., an image in anarrangement suitable for printing) comprising a plurality of digitallabel images 417. In some embodiments, an arrangement suitable forprinting may be configured such that the digital label images 417 arearranged and/or scaled in a manner so as to fit onto a standard sizedpaper when printed, such as industry-standard and/or user selectedprinter paper and/or label paper.

In some embodiments, server 110 may dynamically generate the content ofvirtual label interface 402 e each time it is displayed. For example, insome embodiments, server 110 may generate virtual label interface 402 ebased on the respective optical codes associated with each digital labelentry, the respective data profiles associated with each digital labelentry, the respective names of digital label entries assigned by theuser, and/or other information. In other embodiments, server 110 maydynamically generate virtual label interface 402 e based on adetermination as to whether one or more optical codes respectivelyassociated with digital label entries have previously been scannedand/or registered. For example, virtual label interface 402 e maycomprise one or more status indicators 418 a-418 b corresponding to eachdigital label entry represented by the interface.

As shown by status indicator 418 b in FIG. 4E, in accordance with adetermination that the optical code associated with a digital labelentry has previously been scanned and/or registered, server 110 mayremove, obscure, and/or otherwise modify the optical code from virtuallabel interface 402 e. In the example shown, the optical code is removedand replaced the by an “In Use” visual indicator to (a) indicate to auser that the code is registered and to (b) prevent the user fromre-printing the label and attempting to re-use it in association with adifferent object to be tracked. Alternatively, as shown by statusindicator 418 a in FIG. 4E, in accordance with a determination that theoptical code associated with a digital label entry has not previouslybeen scanned and/or registered, server 110 may display the optical codeas part of virtual label interface 402 e. In some embodiments, removal,obfuscation, and/or modification of an optical code and/or theassociated digital label image 417 may be performed without rearrangingany of the visual representations of labels on the sheet; that is, ablank space may be maintained on a virtual visual representation of asheet, following registration of a label, at the location on the sheetwhere the unmodified virtual visual representation of the labelpreviously would have been displayed. In this way, a virtual visualrepresentation of a sheet of labels may visually reflect a correspondingphysical sheet of labels/stickers, in that labels that have been removedfrom a sheet and registered for use may be virtually visually “removed”from the virtual visual representation of the sheet, while labels thathave not yet been removed from the sheet and registered for use maycontinue to be virtually visually represented in the same position onthe virtual visual representation of the sheet.

FIGS. 5A-D show various graphical user interfaces 502 a-502 d forentering and transmitting data, in accordance with some embodiments.Interfaces 502 a-502 d allow a user to enter and transmit measurementdata and other information corresponding to a detected optical codeassociated with an object.

In some embodiments, interfaces 502 a-502 d may be displayed by mobiledevice 108 of system 100. In other embodiments, interfaces 502 a-502 dmay be displayed by any electronic computing device, such as a laptopcomputer, desktop computer, smart-phone, tablet, or other electroniccomputing device configured to display one or more of interfaces 502a-502 d and to receive one or more inputs from a user, as discussedherein, to enter measurement data or other information. In someembodiments, execution of all or part of method 300, as discussed above,may include displaying one or more of the interfaces shown in FIGS.5A-D.

Below, interfaces 502 a-502 d are discussed with respect to FIGS. 5A-5Din greater detail. Interfaces 502 a-502 d may, in some embodiments, beinterrelated interfaces of a single program or application configured tobe used in connection with one another. For example, each of theinterfaces 502 a-502 d may be different screens that are selectivelyaccessible from a mobile application or other computer programconfigured to work in conjunction with one or more electronic devices inorder to enter data into a data collection system.

FIG. 5A shows label registration interface 502 a, according to someembodiments. Label registration interface 502 a may, in someembodiments, be an interface configured to allow a user to register alabel after mobile device 108 detects, by one or more optical sensors ofmobile device 108, an optical code corresponding to a label.

When an optical code is detected by mobile device 108, mobile device 108may prompt the user to register the label—that is, enter a name to beassociated with the object—if the optical code has not previously beensuccessfully registered. In some embodiments, the name may be an ordernumber, airway bill, house airway bill, product identification number,room number, refrigerator number, package information, or any othername. The name need not be unique.

In some embodiments, label registration interface 502 a may compriseregistration name field 504 and registration submission icon 506. Insome embodiments, registration name field 504 may be a text fieldconfigured to accept input from a user. In some embodiments, a user mayenter a name in registration name field 504 to be associated with thedetected label. After a user has entered information in registrationname field 504, the user may select registration submission icon 506 tocause mobile device 108 to transmit the registration information toserver 110. In some embodiments, registration icon 506 may be aninteractive affordance, in that it may be clicked, tapped, pressed, orotherwise selected in order to cause mobile device 108 to transmit theregistration information to server 110.

FIG. 5B shows measurement entry interface 502 b, according to someembodiments. Measurement interface 502 b may, in some embodiments, be aninterface configured to allow a user to enter one or more measurementsassociated with an object.

In some embodiments, measurement entry interface 502 b may comprise oneor more measurement toggle icons 508 that allow a user to select forwhich measurement data is to be entered, and/or to select parameterscorresponding to a particular measurement. For example, toggle icon 508may allow a user to select between a temperature measurement and apressure measurement. Additionally or alternatively, measurement toggleicon 508 may allow a user to select the units in which a measurement areto be entered, such as selecting whether a temperature measurement is tobe entered in degrees Celsius or degrees Fahrenheit, as shown in FIG.5B. In some embodiments, measurement toggle icons 508 may be interactiveaffordances, in that they may be clicked, tapped, pressed, or otherwiseselected in order to switch between measurements to be entered and/orunits to be used.

In some embodiments, measurement entry interface 502 b may comprisemeasurement field 510. In some embodiments, measurement field 510 may bea text field configured to accept input from a user. In someembodiments, measurement field 510 may be configured to only acceptcertain types of input, such as integers, decimals, alpha-numeric text,or other forms of input. In other embodiments, measurement field 510 maycomprise a drop-down menu or number-wheel interface configured to allowa user to choose a measurement value from a pre-defined set of numbers.

In some embodiments, a user may enter measurement data in measurementfield 510 to be associated with the detected label. After a user hasentered information in measurement field 510, the user may select ameasurement submission icon to cause mobile device 108 to transmit themeasurement data to server 110.

FIG. 5C shows event entry interface 502 c, according to someembodiments. Event entry interface 502 c may, in some embodiments, be aninterface configured to allow a user to enter one or more eventsassociated with an object. In some embodiments, interface 502 c may be ascrolled-down version of interface 502 b, in that the options andfunctionalities presented in interface 502 c may be available inaddition to or as one or more alternate options to the options andfunctionalities presented in interface 502 b.

In some embodiments, event entry interface 502 c may comprise one ormore event fields 512. In some embodiments, event field 512 may be apre-defined list of events from which a user may choose an event toassociate with the present scan of an optical code. In otherembodiments, event field 512 may be a drop-down menu or wheel-interfacethat permits a user to choose an event from a pre-defined set of events.In some embodiments, event field 512 may be dynamically populated with alist of permissible events based on the events that the optical code'scorresponding data profile has been defined to accept. In someembodiments, the list or set of available events that are presented to auser in interface 502 c may correspond to events entered in a dataprofile definition interface such as interface 402 a, as discussed abovewith reference to FIG. 4A.

Event field 512 may also be a text field configured to accept input froma user. A user may enter text into event field 512 to identify an eventto be associated with the corresponding optical code. In someembodiments, event fields 512 may be interactive affordances, in thatthey may be clicked, tapped, pressed, or otherwise selected in order toselect the corresponding event and/or to activate additionalfunctionality of the graphical user interface. After a user has selectedone or more of event fields 512 and/or entered information correspondingto the selected event, the user may select an event submission icon tocause mobile device 108 to transmit the event data to server 110.

FIG. 5D shows photograph entry interface 502 d, according to someembodiments. Photograph entry interface 502 d may, in some embodiments,be an interface configured to allow a user to enter one or morephotographs associated with an object. In some embodiments, mobiledevice 108 may automatically display photograph entry interface 502 dafter a user has submitted measurement and/or event information. Inother embodiments, a user may select a photograph icon to cause mobiledevice 108 to display photograph entry interface 502 d.

In some embodiments, photograph entry interface 502 d may comprise photoselection affordance 514. Photo selection affordance 514 may allow auser to choose the source of a photograph to be transmitted. In someembodiments, photo selection affordance 514 may allow a user to chooseto engage a camera associated with mobile device 108 to take aphotograph to transmit to server 110. In other embodiments, photoselection affordance 514 may allow a user to choose to select aphotograph stored in the memory of mobile device 108 to transmit toserver 110.

FIG. 5D is an exemplary depiction of an interface displayed by mobiledevice 108 for prompting the entry of a photograph, according to someembodiments. In some embodiments, the data profile may be defined toaccept (and in some embodiments to require) photographs. The mobileinterface may prompt the user to take a photograph of and/or associatedwith the object, or to select a photograph stored in the memory ofmobile device 108, such that the captured and/or selected photograph maybe transmitted from mobile device 108 in association with otherinformation transmitted regarding the measurements taken or eventsrecorded. In some embodiments, photo selection affordance 514 may beinteractive affordances, in that they may be clicked, tapped, pressed,or otherwise selected in order to activate functionality of thegraphical user interface. After a user has selected a photograph to betransmitted, the user may select a photo submission icon to cause mobiledevice 108 to transmit the photograph to server 110.

FIG. 6 is a depiction of a physical label in the form of a printedsticker, according to some embodiments. In some embodiments, server 110may generate digital label images associated with a digital label entryin a printable form. In some embodiments, server 110 may generateprintable form images that comprise a plurality of digital label imagesin an arrangement suitable for printing. In some embodiments, thedigital label images may be arranged in a manner suitable for printingto adhesive paper suitable for printing stickers. In some embodiments,the digital label images may be arranged into a grid or array suitablefor printing the labels on commercially available adhesive label paper,such as Avery 5163 Shipping Labels.

The digital label images may be grouped according to their data profile,names, and/or other property. Printed labels may be adhered to (ornearby to) measurable objects to identify the objects in the system.

FIG. 7 illustrates an example of a computer in accordance with oneembodiment. Computer 700 can be a component of a data collection systemfor configuring the system and viewing the collected data. In someembodiments, computer 700 is configured to execute a method forconfiguring a data collection system, such as method 200 of FIG. 2.Alternatively, computer 700 can be configured to execute a method formeasuring and recording a characteristic of an object, such as method300 of FIG. 3.

Computer 700 can be a host computer connected to a network. Computer 700can be a client computer or a server. As shown in FIG. 7, computer 700can be any suitable type of microprocessor-based device, such as apersonal computer, workstation, server, videogame console, or handheldcomputing device, such as a phone or tablet. The computer can include,for example, one or more of processor 701, input device 702, outputdevice 703, storage 704, and communication device 705. Input device 702can generally correspond to those described above and can either beconnectable or integrated with the computer.

Input device 702 can be any suitable device that provides input, such asa touch screen or monitor, keyboard, mouse, or voice-recognition device.Output device 703 can be any suitable device that provides output, suchas a touch screen, monitor, printer, disk drive, or speaker.

Storage 704 can be any suitable device that provides storage, such as anelectrical, magnetic, or optical memory, including a RAM, cache, harddrive, CD-ROM drive, tape drive, or removable storage disk.Communication device 705 can include any suitable device capable oftransmitting and receiving signals over a network, such as a networkinterface chip or card. The components of the computer can be connectedin any suitable manner, such as via a physical bus or wirelessly.Storage 704 can be a non-transitory computer-readable storage mediumcomprising one or more programs, which, when executed by one or moreprocessors, such as processor 701, cause the one or more processors toexecute methods described herein.

Software 706, which can be stored in storage 704 and executed byprocessor 701, can include, for example, the programming that embodiesthe functionality of the present disclosure (e.g., as embodied in thesystems, computers, servers, and/or devices as described above). In someembodiments, software 706 can be implemented and executed on acombination of servers such as application servers and database servers.

Software 706, or part thereof, can also be stored and/or transportedwithin any computer-readable storage medium for use by or in connectionwith an instruction execution system, apparatus, or device, such asthose described above, that can fetch and execute instructionsassociated with the software from the instruction execution system,apparatus, or device. In the context of this disclosure, acomputer-readable storage medium can be any medium, such as storage 704,that can contain or store programming for use by or in connection withan instruction execution system, apparatus, or device.

Software 706 can also be propagated within any transport medium for useby or in connection with an instruction execution system, apparatus, ordevice, such as those described above, that can fetch and executeinstructions associated with the software from the instruction executionsystem, apparatus, or device. In the context of this disclosure, atransport medium can be any medium that can communicate, propagate, ortransport programming for use by or in connection with an instructionexecution system, apparatus, or device. The transport-readable mediumcan include, but is not limited to, an electronic, magnetic, optical,electromagnetic, or infrared wired or wireless propagation medium.

Computer 700 may be connected to a network, which can be any suitabletype of interconnected communication system. The network can implementany suitable communications protocol and can be secured by any suitablesecurity protocol. The network can comprise network links of anysuitable arrangement that can implement the transmission and receptionof network signals, such as wireless network connections, T1 or T3lines, cable networks, DSL, or telephone lines.

Computer 700 can implement any operating system suitable for operatingthe network. Software 706 can be written in any suitable programminglanguage, such as C, C++, Java, or Python. In various embodiments,application software embodying the functionality of the presentdisclosure can be deployed in different configurations, such as in aclient/server arrangement or through a web browser as a Web-basedapplication or Web service, for example.

The foregoing description sets forth exemplary models, parameters andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments. Theillustrative embodiments described above are not intended to beexhaustive or to limit the disclosure to the precise forms disclosed.Many modifications and variations are possible in view of the aboveteachings. The embodiments were chosen and described to best explain theprinciples of the disclosed techniques and their practical applications.Others skilled in the art are thereby enabled to best utilize thetechniques and various embodiments with various modifications as aresuited to the particular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying figures, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims. In the foregoing description of the disclosure andembodiments, reference is made to the accompanying drawings, in whichare shown, by way of illustration, specific embodiments that can bepracticed. It is to be understood that other embodiments and examplescan be practiced, and changes can be made without departing from thescope of the present disclosure.

Although the foregoing description uses terms first, second, etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. In addition, it is also to be understood that the singularforms “a,” “an,” and “the” used in the foregoing description areintended to include the plural forms as well, unless the context clearlyindicates otherwise. It is also to be understood that the term “and/or”as used herein refers to and encompasses any and all possiblecombinations of one or more of the associated listed items. It isfurther to be understood that the terms “includes, “including,”“comprises,” and/or “comprising,” when used herein, specify the presenceof stated features, integers, steps, operations, elements, components,and/or units but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,units, and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

The present disclosure also relates to a device for performing theoperations herein. This device may be specially constructed for therequired purposes, or it may include a general purpose computerselectively activated or reconfigured by a computer program stored inthe computer. Such a computer program may be stored in a non-transitory,computer readable storage medium, such as, but not limited to, any typeof disk, including floppy disks, optical disks, CD-ROMs,magnetic-optical disks, read-only memories (ROMs), random accessmemories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, applicationspecific integrated circuits (ASICs), or any type of media suitable forstoring electronic instructions, and each coupled to a computer systembus. Furthermore, the computers referenced in this disclosure mayinclude a single processor or may be architectures employing multipleprocessor designs for increased computing capability.

The methods, devices, and systems described herein are not inherentlyrelated to any particular computer or other apparatus. Variousgeneral-purpose systems may also be used with programs in accordancewith the teachings herein, or it may prove convenient to construct amore specialized apparatus to perform the required method steps. Therequired structure for a variety of these systems will appear from thedescription below. In addition, the present disclosure is not describedwith reference to any particular programming language. It will beappreciated that a variety of programming languages may be used toimplement the teachings of the present disclosure as described herein.

1. A method for detecting and recording event information associatedwith an object, comprising: at a device comprising a display, an opticalsensor, a GPS sensor, one or more processors, and memory: detecting, bythe optical sensor, an optical code, wherein the optical code isphysically associated with an object; in response to detecting theoptical code: decoding an identifying value encoded in the optical code;and transmitting geographic information from the GPS sensor to a remoteserver, wherein the geographic information is transmitted in accordancewith the decoded identifying value; and transmitting event informationassociated with the object, the event information being distinct fromthe geographic information, to the remote server, wherein the eventinformation is transmitted in accordance with the decoded identifyingvalue.
 2. The method of claim 1, further comprising: in response todetecting the optical code, displaying a prompt for a user to enterevent information associated with the object.
 3. The method of claim 2,wherein displaying the prompt comprises displaying a list of eventtypes.
 4. The method of claim 1, wherein the identifying value uniquelycorresponds to an entry in a database.
 5. The method of claim 4, furthercomprising: in response to detecting the optical code, in accordancewith a determination that registration transmission has not previouslybeen transmitted to the remote server in response to detection of theoptical code, displaying a registration interface comprising a userinterface object configured to accept a user input comprisinginformation associated with registering the optical code; detecting aninstruction from the user to transmit the information associated withregistering the optical code; and in response to receiving theinstruction to transmit the information associated with registering theoptical code, transmitting an instruction to the remote server toregister the optical code by uniquely associating the entry in thedatabase with the information associated with registering the opticalcode.
 6. The method of claim 5, wherein the information associated withregistering the optical code comprises an identifier associated with theobject.
 7. The method of claim 4, wherein the identifying valuecomprises a URL corresponding to the entry in the database.
 8. Themethod of claim 1, wherein the optical code comprises a QR code.
 9. Themethod of claim 1, wherein the event information corresponds to an eventthat is designated as a final event.
 10. The method of claim 1,comprising: at a server: receiving the geographic information andreceiving the event information associated with the object; and inresponse to receiving the event information associated with the object,storing a data entry indicating the geographic information andindicating the event information in a database.
 11. The method of claim10, comprising, at the server: in response to receiving the eventinformation, determining that the event information designates a finalevent; and in response to determining that the event informationdesignates a final event, updating a digital label entry such that theserver will no longer accept event information for the object.
 12. Themethod of claim 10, comprising, at the server: in response to receivingthe event information, determining that the event information designatesa final event; and in response to determining that the event informationdesignates a final event, updating a digital label entry such that theoptical code is deactivated.
 13. A device for detecting and recordingevent information associated with an object, the device comprising adisplay, an optical sensor, a GPS sensor, one or more processors, andmemory storing instructions executable by the one or more processors tocause the device to: detect, by the optical sensor, an optical code,wherein the optical code is physically associated with an object; inresponse to detecting the optical code: decode an identifying valueencoded in the optical code; and transmit geographic information fromthe GPS sensor to a remote server, wherein the geographic information istransmitted in accordance with the decoded identifying value; andtransmit event information associated with the object, the eventinformation being distinct from the geographic information, to theremote server, wherein the event information is transmitted inaccordance with the decoded identifying value.
 14. A non-transitorycomputer-readable storage medium storing instructions for detecting andrecording event information associated with an object, the instructionsconfigured to be executed by one or more processors of a devicecomprising a display, an optical sensor, a GPS sensor, and one or moreprocessors, the instructions configured to cause the device to: detect,by the optical sensor, an optical code, wherein the optical code isphysically associated with an object; in response to detecting theoptical code: decode an identifying value encoded in the optical code;and transmit geographic information from the GPS sensor to a remoteserver, wherein the geographic information is transmitted in accordancewith the decoded identifying value; and transmit event informationassociated with the object, the event information being distinct fromthe geographic information, to the remote server, wherein the eventinformation is transmitted in accordance with the decoded identifyingvalue.
 15. A method for configuring a data collection system,comprising: at a system comprising a display, one or more processors,and memory: detecting a first user input, wherein the first user inputcomprises an instruction to generate a set of database entries formonitoring respective objects, and wherein the first user inputindicates a set of event types associated with the objects to bemonitored; in response to detecting the first user input: creating a setof database entries, wherein each entry of the set of database entriesis configured to store data regarding the event types associated withthe respective objects; and generating a set of optical codes, whereineach code of the set of optical codes uniquely corresponds to one of thedatabase entries created; detecting a second user input, wherein thesecond user input comprises an instruction to display a plurality ofimages associated respectively with a subset of the set of databaseentries, wherein each image of the plurality of images uniquelycorresponds to a respective one of the set of database entries; and inresponse to detecting the second user input, displaying a dynamic visualrepresentation of the plurality of images, wherein, for each of theplurality of images, the image visually indicates whether the system hasreceived registration information regarding association of a physicalinstance of the corresponding optical code with one of the objects. 16.The method of claim 15, wherein the data regarding the event typescomprises a predefined list of events.
 17. The method of claim 15,wherein the data regarding the event types designates an event as afinal event.
 18. The method of claim 15, wherein the first user inputcomprises a selection by the user of a data profile, wherein the dataprofile indicates the event types associated with the objects to bemonitored.
 19. The method of claim 15, wherein: the dynamic visualrepresentation indicates that the system has received registrationinformation for a first one of the images by not displaying a firstcorresponding optical code as a part of the first image; and the dynamicvisual representation indicates that the system has not receivedregistration information for a second one of the images by displaying asecond corresponding optical code as a part of the second image.
 20. Adata collection system, the system comprising a display, one or moreprocessors, and memory storing instructions executable by the one ormore processors to cause the system to: detect a first user input,wherein the first user input comprises an instruction to generate a setof database entries for monitoring respective objects, and wherein thefirst user input indicates a set of event types associated with theobjects to be monitored; in response to detecting the first user input:create a set of database entries, wherein each entry of the set ofdatabase entries is configured to store data regarding the event typesassociated with the respective objects; and generate a set of opticalcodes, wherein each code of the set of optical codes uniquelycorresponds to one of the database entries created; detect a second userinput, wherein the second user input comprises an instruction to displaya plurality of images associated respectively with a subset of the setof database entries, wherein each image of the plurality of imagesuniquely corresponds to a respective one of the set of database entries;and in response to detecting the second user input, display a dynamicvisual representation of the plurality of images, wherein, for each ofthe plurality of images, the image visually indicates whether the systemhas received registration information regarding association of aphysical instance of the corresponding optical code with one of theobjects.
 21. A non-transitory computer-readable storage medium storinginstructions for configuring a data collection system, the instructionsconfigured to be executed by one or more processors of a systemcomprising a display and one or more processors, the instructionsconfigured to cause the system to: detect a first user input, whereinthe first user input comprises an instruction to generate a set ofdatabase entries for monitoring respective objects, and wherein thefirst user input indicates a set of event types associated with theobjects to be monitored; in response to detecting the first user input:create a set of database entries, wherein each entry of the set ofdatabase entries is configured to store data regarding the event typesassociated with the respective objects; and generate a set of opticalcodes, wherein each code of the set of optical codes uniquelycorresponds to one of the database entries created; detect a second userinput, wherein the second user input comprises an instruction to displaya plurality of images associated respectively with a subset of the setof database entries, wherein each image of the plurality of imagesuniquely corresponds to a respective one of the set of database entries;and in response to detecting the second user input, display a dynamicvisual representation of the plurality of images, wherein, for each ofthe plurality of images, the image visually indicates whether the systemhas received registration information regarding association of aphysical instance of the corresponding optical code with one of theobjects.
 22. A data measurement and collection system, comprising: aserver configured to: detect a first user input, wherein the first userinput comprises an instruction to generate a set of database entries formonitoring respective objects, and wherein the first user inputindicates a set of event types associated with the objects to bemonitored; in response to detecting the first user input: create a setof database entries, wherein each entry of the set of database entriesis configured to store data regarding the event types associated withthe respective objects; and generate a set of optical codes, whereineach code of the set of optical codes uniquely corresponds to one of thedatabase entries created; and a mobile electronic device comprising anoptical sensor and a GPS sensor, the mobile electronic device configuredto: detect, by the optical sensor, one of the optical codes of the setof optical codes, wherein the optical code is physically associated withone of the objects; and in response to detecting the optical code:transmit geographic information from the GPS sensor to the server; andtransmit information event information associated with the object, theevent information being distinct from the geographic information, to theserver.
 23. The system of claim 22, wherein the mobile electronic deviceis configured to, in response to detecting the optical code, display agraphical user interface configured to accept a user input indicatingthe event information associated with the object.